The Cisco ASA remote access VPN server must be configured to generate log records containing information to establish the source of the events.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-239973	CASA-VN-000520	SV-239973r666325_rule		Low

Description

Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment and provide forensic analysis, security personnel need to know the source of the event. In addition to logging where events occur within the network, the log records must also identify sources of events such as IP addresses, processes, and node or device names.

STIG	Date
Cisco ASA VPN Security Technical Implementation Guide	2021-08-16

Details

Check Text ( C-43206r666323_chk )

Verify the ASA generates log records containing information to establish the source of the events as shown in the example below. logging class vpn trap notifications logging class vpnc trap notifications logging class vpnfo trap notifications logging class webfo trap notifications logging class webvpn trap notifications logging class svc trap notifications Note: A logging list can be used as an alternative to using class. If the ASA does not generate log records containing information to establish the source of the events, this is a finding.

Fix Text (F-43165r666324_fix)

Configure the ASA to generate log records containing information to establish the source of the events as shown in the example below. ciscoasa(config)# logging class vpn trap notifications ciscoasa(config)# logging class vpnc trap notifications ciscoasa(config)# logging class vpnfo trap notifications ciscoasa(config)# logging class webvpn trap notifications ciscoasa(config)# logging class webfo trap notifications ciscoasa(config)# logging class svc trap notifications ciscoasa(config)# end